Secondary authorization at PDU session establishment at home routed roaming

ABSTRACT

Exemplary embodiments include a method, performed by a session management function (V-SMF) of a visited public land mobile network (VPLMN), for establishing a user-requested PDU session to be routed through the user&#39;s home PLMN (HPLMN). Such embodiments include receiving, from an access management function (AMF) in the HPLMN, a first request to establish a home-routed PDU session, wherein the first request identifies an SMF (H-SMF) in the HPLMN. Such embodiments also include sending, to the H-SMF, a second request to create the home-routed PDU session. The second request can include an identifier of a resource in the V-SMF associated with the PDU session; and one or more indicators of whether the V-SMF supports respective one or more features related to receiving, from the H-SMF, an identifier of a resource in the H-SMF that is associated with the PDU session. Embodiments also include complementary methods performed by the H-SMF.

RELATED APPLICATIONS

The present application claims priority to U.S. provisional appl. No.62/805,128 filed on Feb. 13, 2019, the entirety of which is incorporatedherein by reference for all purposes.

TECHNICAL FIELD

The present application relates generally to the field oftelecommunications and more specifically to facilitate establishment ofdata sessions when a user is roaming from the user's home network intoanother network.

BACKGROUND

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsand/or procedures disclosed herein do not have to be performed in theexact order disclosed, unless a step is explicitly described asfollowing or preceding another step and/or where it is implicit that astep must follow or precede another step. Any feature of any of theembodiments disclosed herein can be applied to any other embodiment,wherever appropriate. Likewise, any advantage of any of the embodimentscan apply to any other embodiments, and vice versa. Other objectives,features and advantages of the enclosed embodiments will be apparentfrom the following description.

Long Term Evolution (LTE) is an umbrella term for so-calledfourth-generation (4G) radio access technologies developed within theThird-Generation Partnership Project (3GPP) and initially standardizedin Releases 8 and 9, also known as Evolved UTRAN (E-UTRAN). LTE istargeted at various licensed frequency bands and is accompanied byimprovements to non-radio aspects commonly referred to as SystemArchitecture Evolution (SAE), which includes Evolved Packet Core (EPC)network. LTE continues to evolve through subsequent releases. One of thefeatures of Release 11 is an enhanced Physical Downlink Control Channel(ePDCCH), which has the goals of increasing capacity and improvingspatial reuse of control channel resources, improving inter-cellinterference coordination (ICIC), and supporting antenna beamformingand/or transmit diversity for control channel.

An overall exemplary architecture of a network comprising LTE and SAE isshown in FIG. 1. E-UTRAN 100 comprises one or more evolved Node B's(eNB), such as eNBs 105, 110, and 115, and one or more user equipment(UE), such as UE 120. As used within the 3GPP standards, “userequipment” or “UE” means any wireless communication device (e.g.,smartphone or computing device) that is capable of communicating with3GPP-standard-compliant network equipment, including E-UTRAN as well asUTRAN and/or GERAN, as the third-(“3G”) and second-generation (“2G”)3GPP radio access networks are commonly known.

As specified by 3GPP, E-UTRAN 100 is responsible for all radio-relatedfunctions in the network, including radio bearer control, radioadmission control, radio mobility control, scheduling, and dynamicallocation of resources to UEs in uplink and downlink, as well assecurity of the communications with the UE. These functions reside inthe eNBs, such as eNBs 105, 110, and 115. The eNBs in the E-UTRANcommunicate with each other via the X1 interface, as shown in FIG. 1.The eNBs also are responsible for the E-UTRAN interface to the EPC 130,specifically the S1 interface to the Mobility Management Entity (MME)and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and138 in FIG. 1. Generally speaking, the MME/S-GW handles both the overallcontrol of the UE and data flow between the UE and the rest of the EPC.More specifically, the MME processes the signaling (e.g., control plane)protocols between the UE and the EPC, which are known as the Non-AccessStratum (NAS) protocols. The S-GW handles all Internet Protocol (IP)data packets (e.g., data or user plane) between the UE and the EPC, andserves as the local mobility anchor for the data bearers when the UEmoves between eNBs, such as eNBs 105, 110, and 115.

EPC 130 can also include a Home Subscriber Server (HSS) 131, whichmanages user- and subscriber-related information. HSS 131 can alsoprovide support functions in mobility management, call and sessionsetup, user authentication and access authorization. The functions ofHSS 131 can be related to the functions of legacy Home Location Register(HLR) and Authentication Centre (AuC) functions or operations.

In some embodiments, HSS 131 can communicate with a user data repository(UDR)—labelled EPC-UDR 135 in FIG. 1—via a Ud interface. The EPC-UDR 135can store user credentials after they have been encrypted by AuCalgorithms. These algorithms are not standardized (i.e.,vendor-specific), such that encrypted credentials stored in EPC-UDR 135are inaccessible by any other vendor than the the vendor of HSS 131.

FIG. 2A shows a high-level block diagram of an exemplary LTEarchitecture in terms of its constituent entities—UE, E-UTRAN, andEPC—and high-level functional division into the Access Stratum (AS) andthe Non-Access Stratum (NAS). FIG. 2A also illustrates two particularinterface points, namely Uu (UE/E-UTRAN Radio Interface) and S1(E-UTRAN/EPC interface), each using a specific set of protocols, i.e.,Radio Protocols and S1 Protocols. Each of the two protocols can befurther segmented into user plane (or “U-plane”) and control plane (or“C-plane”) protocol functionality. On the Uu interface, the U-planecarries user information (e.g., data packets) while the C-plane iscarries control information between UE and E-UTRAN.

FIG. 2B illustrates a block diagram of an exemplary C-plane protocolstack on the Uu interface comprising Physical (PHY), Medium AccessControl (MAC), Radio Link Control (RLC), Packet Data ConvergenceProtocol (PDCP), and Radio Resource Control (RRC) layers. The PHY layeris concerned with how and what characteristics are used to transfer dataover transport channels on the LTE radio interface. The MAC layerprovides data transfer services on logical channels, maps logicalchannels to PHY transport channels, and reallocates PHY resources tosupport these services. The RLC layer provides error detection and/orcorrection, concatenation, segmentation, and reassembly, reordering ofdata transferred to or from the upper layers. The PHY, MAC, and RLClayers perform identical functions for both the U-plane and the C-plane.The PDCP layer provides ciphering/deciphering and integrity protectionfor both U-plane and C-plane, as well as other functions for the U-planesuch as header compression.

FIG. 2C shows a block diagram of an exemplary LTE radio interfaceprotocol architecture from the perspective of the PHY. The interfacesbetween the various layers are provided by Service Access Points (SAPs),indicated by the ovals in FIG. 2C. The PHY layer interfaces with the MACand RRC protocol layers described above. The MAC provides differentlogical channels to the RLC protocol layer (also described above),characterized by the type of information transferred, whereas the PHYprovides a transport channel to the MAC, characterized by how theinformation is transferred over the radio interface. In providing thistransport service, the PHY performs various functions including errordetection and correction; rate-matching and mapping of the codedtransport channel onto physical channels; power weighting, modulation;and demodulation of physical channels; transmit diversity, beamformingmultiple input multiple output (MIMO) antenna processing; and providingradio measurements to higher layers, such as RRC.

Generally speaking, a physical channel corresponds a set of resourceelements carrying information that originates from higher layers.Downlink (i.e., eNB to UE) physical channels provided by the LTE PHYinclude Physical Downlink Shared Channel (PDSCH), Physical MulticastChannel (PMCH), Physical Downlink Control Channel (PDCCH), RelayPhysical Downlink Control Channel (R-PDCCH), Physical Broadcast Channel(PBCH), Physical Control Format Indicator Channel (PCFICH), and PhysicalHybrid ARQ Indicator Channel (PHICH). In addition, the LTE PHY downlinkincludes various reference signals, synchronization signals, anddiscovery signals.

PDSCH is the main physical channel used for unicast downlink datatransmission, but also for transmission of RAR (random access response),certain system information blocks, and paging information. PBCH carriesthe basic system information, required by the UE to access the network.PDCCH is used for transmitting downlink control information (DCI),mainly scheduling decisions, required for reception of PDSCH, and foruplink scheduling grants enabling transmission on PUSCH.

Uplink (i.e., UE to eNB) physical channels provided by the LTE PHYinclude Physical Uplink Shared Channel (PUSCH), Physical Uplink ControlChannel (PUCCH), and Physical Random Access Channel (PRACH). Inaddition, the LTE PHY uplink includes various reference signalsincluding demodulation reference signals (DM-RS), which are transmittedto aid the eNB in the reception of an associated PUCCH or PUSCH; andsounding reference signals (SRS), which are not associated with anyuplink channel. PUSCH is the uplink counterpart to the PDSCH. PUCCH isused by UEs to transmit uplink control information, including HARQacknowledgements, channel state information reports, etc. PRACH is usedfor random access preamble transmission.

In 3GPP, a study item on a new radio interface for a fifth-generation(5G) cellular (e.g., wireless) network has recently been completed. 3GPPis now standardizing this new radio interface, often abbreviated by NR(New Radio). FIG. 3 illustrates a high-level view of the 5G networkarchitecture, consisting of a Next Generation RAN (NG-RAN) 399 and a 5GCore (5GC) 398. NG-RAN 399 can include a set of gNodeB's (gNBs)connected to the 5GC via one or more NG interfaces, such as gNBs 300,350 connected via interfaces 302, 352, respectively. In addition, thegNBs can be connected to each other via one or more Xn interfaces, suchas Xn interface 340 between gNBs 300 and 350. With respect the the NRinterface to UEs, each of the gNBs can support frequency divisionduplexing (FDD), time division duplexing (TDD), or a combinationthereof.

NG-RAN 399 is layered into a Radio Network Layer (RNL) and a TransportNetwork Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logicalnodes and interfaces between them, is defined as part of the RNL. Foreach NG-RAN interface (NG, Xn, F1) the related TNL protocol and thefunctionality are specified. The TNL provides services for user planetransport and signaling transport. In some exemplary configurations,each gNB is connected to all 5GC nodes within an “AMF Region,” which isdefined in 3GPP TS 23.501. If security protection for CP and UP data onTNL of NG-RAN interfaces is supported, NDS/IP (3GPP TS 33.401) shall beapplied.

The NG RAN logical nodes shown in FIG. 3 (and described in TS 38.401 andTR 38.801) include a central (or centralized) unit (CU or gNB-CU) andone or more distributed (or decentralized) units (DU or gNB-DU). Forexample, gNB 300 in FIG. 3 includes gNB-CU 310 and gNB-DUs 320 and 330.CUs (e.g., gNB-CU 310) are logical nodes that host higher-layerprotocols and perform various gNB functions such controlling theoperation of DUs. Each DU is a logical node that hosts lower-layerprotocols and can include, depending on the functional split, varioussubsets of the gNB functions. As such, each of the CUs and DUs caninclude various circuitry needed to perform their respective functions,including processing circuitry, transceiver circuitry (e.g., forcommunication), and power supply circuitry. Moreover, the terms “centralunit” and “centralized unit” are used interchangeably herein, as are theterms “distributed unit” and “decentralized unit.”

A gNB-CU connects to gNB-DUs over respective F1 logical interfaces, suchas interfaces 322 and 332 shown in FIG. 3. The gNB-CU and connectedgNB-DUs are only visible to other gNBs and the 5GC as a gNB, e.g., theF1 interface is not visible beyond gNB-CU. In the gNB split CU-DUarchitecture illustrated by FIG. 5, DC can be achieved by allowing a UEto connect to multiple DUs served by the same CU or by allowing a UE toconnect to multiple DUs served by different CUs.

FIG. 4 shows a high-level view of an exemplary 5G network architecture,including a Next Generation Radio Access Network (NG-RAN) 499 and a 5GCore (5GC) 498. As shown in the figure, NG-RAN 499 can include gNBs 410(e.g., 410 a,b) and ng-eNBs 420 (e.g., 420 a,b) that are interconnectedwith each other via respective Xn interfaces. The gNBs and ng-eNBs arealso connected via the NG interfaces to 5GC 498, more specifically tothe AMF (Access and Mobility Management Function) 430 (e.g., AMFs 430a,b) via respective NG-C interfaces and to the UPF (User Plane Function)440 (e.g., UPFs 440 a,b) via respective NG-U interfaces.

Each of the gNBs 410 can support the NR radio interface, includingfrequency division duplexing (FDD), time division duplexing (TDD), or acombination thereof. In contrast, each of ng-eNBs 420 supports the LTEradio interface but, unlike conventional LTE eNBs (such as shown in FIG.1), connect to the 5GC via the NG interface.

Deployments based on different 3GPP architecture options (e.g.,EPC-based or 5GC-based) and UEs with different capabilities (e.g., EPCNAS and 5GC NAS) may coexist at the same time within one network (e.g.,PLMN). It is generally assumed that a UE that can support 5GC NASprocedures can also support EPC NAS procedures (e.g., as defined in 3GPPTS 24.301) to operate in legacy networks, such as when roaming. As such,the UE will use EPC NAS or 5GC NAS procedures depending on the corenetwork (CN) by which it is served.

Another change in 5G networks (e.g., in 5GC) is that traditionalpeer-to-peer interfaces and protocols (e.g., those found in LTE/EPCnetworks) are modified by a so-called Service Based Architecture (SBA)in which Network Functions provide one or more services to one or moreservice consumers. This can be done, for example, by Hyper Text TransferProtocol/Representational State Transfer (HTTP/REST) applicationprogramming interfaces (APIs).

The services are composed of various “service operations”, which aremore granular divisions of the overall service functionality. In orderto access a service, both the service name and the targeted serviceoperation must be indicated. The interactions between service consumersand producers can be of the type “request/response” or“subscribe/notify”. In the 5G SBA, network repository functions (NRF)allow every network function to discover the services offered by othernetwork functions, and Data Storage Functions (DSF) allow every networkfunction to store its context.

This architecture model, which further adopts principles likemodularity, reusability and self-containment of network functions, canenable deployments to take advantage of the latest virtualization andsoftware technologies. FIG. 5 shows an exemplary non-roaming 5Greference architecture with service-based interfaces and various networkfunctions within the Control Plane (CP). These include:

-   -   Access and Mobility Management Function (AMF) with Namf        interface;    -   Session Management Function (SMF) with Nsmf interface;    -   User Plane Function (UPF) with Nupf interface;    -   Policy Control Function (PCF) with Npcf interface;    -   Network Exposure Function (NEF) with Nnef interface;    -   Network Repository Function (NRF) with Nnrf interface;    -   Network Slice Selection Function (NSSF) with Nnssf interface;    -   Authentication Server Function (AUSF) with Nausf interface;    -   Application Function (AF) with Naf interface; and    -   Unified Data Management (UDM) with Nudm interface.

The UDM is similar to the HSS in LTE/EPC networks discussed above. UDMsupports Generation of 3GPP AKA authentication credentials, useridentification handling, access authorization based on subscriptiondata, and other subscriber-related functions. To provide thisfunctionality, the UDM uses subscription data (including authenticationdata) stored in the 5GC unified data repository (UDR). In addition tothe UDM, the UDR supports storage and retrieval of policy data by thePCF, as well as storage and retrieval of application data by NEF.

FIG. 6 shows an exemplary roaming 5G reference architecture withservice-based interfaces. In this reference architecture, the user roamsinto a Visited Public Land Mobile Network (VPLMN) that is different thanthe user's Home PLMN (HPLMN). In particular, FIG. 6 shows a roamingarchitecture that supports home-routed data services, in which the homeoperator's administrative domain is involved in the user's data sessionand the UE interfaces the data network (DN) in the HPLMN. From theuser's perspective, the various network functions of the HPLMN shown inthe non-roaming architecture of FIG. 5 are distributed among the HPLMNand VPLMN in the home-routed roaming architecture shown in FIG. 6. Forexample, the AMF is in the VPLMN, the AUSF is in the HPLMN, and the SMFand UPF exist in both (e.g., are split between) VPLMN and HPLMN. Todistinguish between these functions existing in both networks, a prefixof “H” or “V” can be used, such as “H-UPF” and “V-UPF”.

In both roaming and non-roaming scenarios, a user (e.g., a UE) may wantto establish a data session (also referred to as a “PDU session”) with adata network (DN, e.g., Internet) via the 5G network. The session ismanaged by a resource in the SMF which is created by an create Sessionmanagement context request when establishing the session. The term“PDU”, short for “protocol data unit,” is often used to refer to a unitof data specified in a protocol layer and comprising protocol controlinformation and possibly user data. “PDU” is often used interchangeablywith “packet.” A PDU Session establishment may correspond to any of thefollowing:

-   -   a UE initiated PDU Session Establishment procedure;    -   a UE initiated PDU Session handover between 3GPP and non-3GPP        networks;    -   a UE initiated PDU Session handover from LTE to NR (e.g., EPC to        5GC); and    -   a network-triggered PDU Session Establishment procedure. In this        case, the network sends the device trigger message to        application(s) on the UE side. The payload included in Device        Trigger Request message contains information on which        application on the UE side is expected to trigger the PDU        Session establishment request. Based on that information, the        application(s) on the UE side trigger the PDU Session        Establishment procedure.

For a UE-initiated (or UE-requested) PDU session establishment based onhome-routed roaming, functions in the VPLMN often need to exchangeinformation about the user with their peer and/or corresponding functionin the HPLMN. For example, the V-SMF often needs to exchange informationwith the H-SMF. However, various problems and/or difficulties can arisedue to the VPLMN function (e.g., V-SMF) lacking necessary informationabout the corresponding HPLMN function (e.g., H-SMF).

SUMMARY

Accordingly, exemplary embodiments of the present disclosure addressthese and other difficulties in PDU session establishment based onhome-routed roaming techniques.

Exemplary embodiments of the present disclosure include methods and/orprocedures for establishing a user-requested PDU session to be routedthrough the user's HPLMN. The exemplary methods and/or procedures can beperformed by a session management function (e.g., SMF) or node in avisited PLMN that is different than the HPLMN of the user establishingthe PDU session.

The exemplary methods and/or procedures can include receiving, from anaccess management function (AMF) in the VPLMN, a first request toestablish a home-routed PDU session, wherein the first requestidentifies an SMF (H-SMF) in the HPLMN. The exemplary methods and/orprocedures can also include sending, to the H-SMF, a second request tocreate the home-routed PDU session. The second request can include anidentifier of a resource in the V-SMF associated with the PDU session.The second request can also include one or more indicators of whetherthe V-SMF supports respective one or more features related to receiving,from the H-SMF, an identifier of a resource in the H-SMF that isassociated with the PDU session.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports early delivery of the identifier of the resourcein the H-SMF. In such embodiments, the exemplary methods and/orprocedures can also include receiving from the H-SMF, a third requestthat includes the identifier of the resource in the H-SMF, the thirdrequest being received before receiving any other messages from theH-SMF.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports delayed sending of a response to a thirdrequest. In such embodiments, the exemplary methods and/or procedurescan also include receiving, from the H-SMF, a third request comprising afurther indicator that the V-SMF should delay sending a response to thethird request until after receiving, from the AMF, authenticationinformation relating to the user. In such embodiments, the exemplarymethods and/or procedures can also include, after receiving theauthentication information from the AMF, sending the response to thethird request to the H-SMF. In such embodiments, the exemplary methodsand/or procedures can also include subsequently receiving a response, tothe second request, comprising the identifier of the resource in theH-SMF.

Other exemplary embodiments of the present disclosure include methodsand/or procedures for establishing a user-requested PDU session to berouted from a user's VPLMN through the user's HPLMN. These exemplarymethods and/or procedures can be performed by a session managementfunction (e.g., SMF) or node in a HPLMN (e.g., a H-SMF) that isdifferent from the VPLMN where the user is initiating the PDU session.

The exemplary methods and/or procedures can include receiving, from aSMF of the VPLMN (V-SMF), a second request to create a home-routed PDUsession. The second request can include an identifier of a resource inthe V-SMF that is associated with the PDU session. The second requestcan also include one or more indicators of whether the V-SMF supportsrespective one or more features related to receiving, from the H-SMF, anidentifier of a resource in the H-SMF that is associated with the PDUsession. The exemplary methods and/or procedures can also include, basedon the one or more indicators, sending one or more messages to theV-SMF, with each message including one of the following: a furtherindicator; and the identifier of the resource in the H-SMF.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports early delivery of the identifier of the resourcein the H-SMF. In such embodiments, one of the messages sent to the V-SMFcan be a third request that includes the identifier of the resource inthe H-SMF, the third request being sent before sending any othermessages to the V-SMF.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports delayed sending of a response to a thirdrequest. In such embodiments, the one or more messages sent to the V-SMFcan be a third request comprising a further indicator that the V-SMFshould delay sending a response to the third request until afterreceiving authentication information relating to the user. In suchembodiments, the exemplary methods and/or procedures can also includereceive the response to the third request from the V-SMF. In suchembodiments, the one or more messages sent to the V-SMF can also includea response, to the second request, comprising the identifier of theresource in the H-SMF, with the response to the second request beingsent after receiving the response to the third request.

Other exemplary embodiments include sesson management nodes, functions,and/or services (e.g., SMF components thereof) configured to performoperations corresponding to the exemplary methods and/or procedures.Other exemplary embodiments include non-transitory, computer-readablemedia storing computer-executable instructions that, when executed by aprocessing circuit comprising a network node, configure the network nodeto perform operations corresponding to the exemplary methods and/orprocedures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level block diagram of an exemplary architecture of theLong-Term Evolution (LTE) Evolved UTRAN (E-UTRAN) and Evolved PacketCore (EPC) network, as standardized by 3GPP.

FIG. 2A is a high-level block diagram of an exemplary E-UTRANarchitecture in terms of its constituent components, protocols, andinterfaces.

FIG. 2B is a block diagram of exemplary protocol layers of thecontrol-plane portion of the radio (Uu) interface between a userequipment (UE) and the E-UTRAN.

FIG. 2C is a block diagram of an exemplary LTE radio interface protocolarchitecture from the perspective of the PHY layer.

FIG. 3 illustrates a high-level view of the 5G network architecture,including split central unit (CU)-distributed unit (DU) splitarchitecture of gNBs.

FIG. 4 illustrates a different high-level view of the 5G networkarchitecture.

FIG. 5 shows an exemplary non-roaming 5G reference architecture withservice-based interfaces and various network functions within thecontrol plane (CP), as further explained in 3GPP TS 23.501.

FIG. 6 shows an exemplary roaming 5G reference architecture withservice-based interfaces that supports home-routed data sessions, asfurther explained in 3GPP TS 23.501.

FIG. 7 shows an exemplary signalling flow of an establishment procedurefor a UE-requested PDU session based on home-routed roaming.

FIG. 8 shows an exemplary signalling flow of a PDU session establishmentauthentication/authorization procedure by a DN AAA server.

FIG. 9 shows an exemplary simplified signalling flow of an establishmentprocedure for a UE-requested PDU session based on home-routed roaming.

FIGS. 10-11 show two exemplary signalling flows for PDU sessionestablishment in a home-routed roaming scenario, according to variousexemplary embodiments of the present disclosure.

FIGS. 12-13 illustrate exemplary methods and/or procedures forestablishing a user-requested PDU session to be routed from a user'svisited PLMN (VPLMN) through the user's home PLMN (HPLMN), according tovarious exemplary embodiments of the present disclosure.

FIG. 14 illustrates an exemplary embodiment of a wireless network, inaccordance with various aspects described herein.

FIG. 15 illustrates an exemplary embodiment of a UE, in accordance withvarious aspects described herein.

FIG. 16 is a block diagram illustrating an exemplary virtualizationenvironment usable for implementation of various embodiments of networknodes described herein.

FIGS. 17-18 are block diagrams of various exemplary communicationsystems and/or networks, in accordance with various aspects describedherein.

FIGS. 19-22 are flow diagrams of exemplary methods and/or procedures fortransmission and/or reception of user data that can be implemented, forexample, in the exemplary communication systems and/or networksillustrated in FIGS. 17-18.

DETAILED DESCRIPTION

Exemplary embodiments briefly summarized above will now be describedmore fully with reference to the accompanying drawings. Thesedescriptions are provided by way of example to explain the subjectmatter to those skilled in the art, and should not be construed aslimiting the scope of the subject matter to only the embodimentsdescribed herein. More specifically, examples are provided below thatillustrate the operation of various embodiments according to theadvantages discussed above. Furthermore, the following terms are usedthroughout the description given below:

-   -   Radio Node: As used herein, a “radio node” can be either a        “radio access node” or a “wireless device.”    -   Radio Access Node: As used herein, a “radio access node” (or        “radio network node”) can be any node in a radio access network        (RAN) of a cellular communications network that operates to        wirelessly transmit and/or receive signals. Some examples of a        radio access node include, but are not limited to, a base        station (e.g., a New Radio (NR) base station (gNB) in a 3GPP        Fifth Generation (5G) NR network or an enhanced or evolved Node        B (eNB) in a 3GPP LTE network), a high-power or macro base        station, a low-power base station (e.g., a micro base station, a        pico base station, a home eNB, or the like), a relay nod, access        point (AP), radio AP, remote radio unit (RRU), remote radio head        (RRH), a multi-standard BS (a.k.a. MSR BS), multi-cell/multicast        coordination entity (MCE), base transceiver station (BTS), base        station controller (BSC), network controller, Node B, etc. Such        terms can also be used to reference to components of a node,        such as a gNB-CU and/or a gNB-DU.    -   Core Network Node: As used herein, a “core network node” is any        type of node in a core network. Some examples of a core network        node include, e.g., a Mobility Management Entity (MME), a Packet        Data Network Gateway (P-GW), a Service Capability Exposure        Function (SCEF), Access and Mobility Management Function (AMF),        User Plane Function (UPF), Home Subscriber Server (HSS), etc.    -   Wireless Device: As used herein, a “wireless device” is any type        of device that has access to (i.e., is served by) a cellular        communications network by wirelessly transmitting and/or        receiving signals to a radio access node(s). Some examples of a        wireless device include, but are not limited to, a UE in a 3GPP        network and a Machine Type Communication (MTC) device.    -   User Equipment: As used herein, a user equipment (or UE, for        short) can be any type of wireless device capable of        communicating with network node or another UE over radio        signals. The UE may also be radio communication device, target        device, device to device (D2D) UE, machine type UE or UE capable        of machine to machine communication (M2M), a sensor equipped        with UE, iPAD, Tablet, mobile terminals, smart phone, laptop        embedded equipped (LEE), laptop mounted equipment (LME), USB        dongles, Customer Premises Equipment (CPE) etc.    -   Network Node: As used herein, a “network node” is any node that        is either part of the radio access network (e.g., a “radio        network node” or “radio access node”) or the core network (e.g.,        a “core network node”) of a cellular communications        network/system.

Note that the description given herein focuses on a 3GPP cellularcommunications system and, as such, 3GPP terminology or terminologysimilar to 3GPP terminology is oftentimes used. However, the conceptsdisclosed herein are not limited to a 3GPP system. And to the extentthat the descriptions of various embodiments refer to NR, such describedembodiments are not limited to NR, but can be adapted in other radioaccess technologies including LTE, UTRA, LTE-Advanced, 5G, NX, NB-IoT,WiFi, BlueTooth, etc.

Furthermore, although the term “cell” is used herein, it should beunderstood that (particularly with respect to 5G NR) beams may be usedinstead of cells and, as such, concepts described herein apply equallyto both cells and beams.

As discussed above, for a UE-initiated (or UE-requested) PDU sessionestablishment based on home-routed roaming, functions in the VPLMN oftenneed to exchange information about the user with their peer and/orcorresponding function in the HPLMN. However, various problems and/ordifficulties can arise due to the VPLMN function (e.g., V-SMF) lackingnecessary information about the corresponding HPLMN function (e.g.,H-SMF). These are discussed below in more detail.

FIG. 7 shows an exemplary signalling flow of an establishment procedurefor a UE-requested PDU session based on home-routed roaming. Althoughthe operations shown in FIG. 7 are labelled with numbers, this labellingis only to facilitate clarity of description, and should not beinterpreted as limiting the operations to occur in the order of theirnumerical labelling. In other words, unless expressly noted otherwise,the operations shown in FIG. 7 can occur in different orders than shown,and can be combined and/or divided to form other operations. Theoperations shown in FIG. 7 are described as follows. To the extent thatthis description refers to 3GPP standards, the relevant portions ofthese standards are incorporated herein by reference.

-   1. From UE to AMF: NAS Message (S-NSSAI(s), DNN, PDU Session ID,    Request type, Old PDU Session ID, N1 SM container (PDU Session    Establishment Request)).

In order to establish a new PDU Session, the UE generates a new PDUSession ID.

The UE initiates the UE Requested PDU Session Establishment procedure bythe transmission of a NAS message containing a PDU Session EstablishmentRequest within the N1 SM container. The PDU Session EstablishmentRequest includes a PDU session ID, Requested PDU Session Type, aRequested SSC mode, 5GSM Capability PCO, SM PDU DN Request Container,Number Of Packet Filters, and optionally Always-on PDU SessionRequested.

The Request Type indicates “Initial request” if the PDU SessionEstablishment is a request to establish a new PDU Session and indicates“Existing PDU Session” if the request refers to an existing PDU Sessionswitching between 3GPP access and non-3GPP access or to a PDU Sessionhandover from an existing PDN connection in EPC. If the request refersto an existing PDN connection in EPC, the S-NSSAI is set as described in3GPP TS 23.501 clause 5.15.7.2.

When Emergency service is required and an Emergency PDU Session is notalready established, a UE shall initiate the UE Requested PDU SessionEstablishment procedure with a Request Type indicating “EmergencyRequest”.

The Request Type indicates “Emergency Request” if the PDU SessionEstablishment is a request to establish a PDU Session for Emergencyservices. The Request Type indicates “Existing Emergency PDU Session” ifthe request refers to an existing PDU Session for Emergency servicesswitching between 3GPP access and non-3GPP access or to a PDU Sessionhandover from an existing PDN connection for Emergency services in EPC.

The 5GSM Core Network Capability is provided by the UE and handled bySMF as defined in 3GPP TS 23.501 clause 5.4.4b. The 5GSM Capability alsoincludes the UE Integrity Protection Maximum Data Rate.

The Number Of Packet Filters indicates the number of supported packetfilters for signalled QoS rules for the PDU Session that is beingestablished. The number of packet filters indicated by the UE is validfor the lifetime of the PDU Session.

The NAS message sent by the UE is encapsulated by the AN in a N2 messagetowards the AMF that should include User location information and AccessType Information.

The PDU Session Establishment Request message may contain SM PDU DNRequest Container containing information for the PDU Sessionauthorization by the external DN.

The UE includes the S-NSSAI from the Allowed NSSAI of the current accesstype. If the Mapping of Allowed NSSAI was provided to the UE, the UEshall provide both the S-NSSAI from the Allowed NSSAI and thecorresponding S-NSSAI from the Mapping Of Allowed NSSAI.

If the procedure is triggered for SSC mode 3 operation, the UE shallalso include the Old PDU Session ID which indicates the PDU Session IDof the on-going PDU Session to be released, in NAS message. The Old PDUSession ID is an optional parameter which is included only in this case.

The AMF receives from the AN the NAS SM message (built in operation 1)together with User Location Information (e.g., Cell Id in case of theNG-RAN).

The UE shall not trigger a PDU Session establishment for a PDU Sessioncorresponding to a LADN when the UE is outside the area of availabilityof the LADN.

If the UE is establishing a PDU session for IMS, and the UE isconfigured to discover the P-CSCF address during connectivityestablishment, the UE shall include an indicator that it requests aP-CSCF IP address(es) within the SM container.

The PS Data Off status is included in the PCO in the PDU SessionEstablishment Request message.

If the UE requests to establish always-on PDU session, the UE includesan Always-on PDU Session Requested indication in the PDU SessionEstablishment Request message.

-   2. The AMF determines that the message corresponds to a request for    a new PDU Session based on that Request Type indicates “initial    request” and that the PDU Session ID is not used for any existing    PDU Session(s) of the UE. If the NAS message does not contain an    S-NSSAI, the AMF determines a default S-NSSAI for the requested PDU    Session either according to the UE subscription, if it contains only    one default S-NSSAI, or based on operator policy. When the NAS    Message contains an S-NSSAI but it does not contain a DNN, the AMF    determines the DNN for the requested PDU Session by selecting the    default DNN for this S-NSSAI if the default DNN is present in the    UE's Subscription Information; otherwise the serving AMF selects a    locally configured DNN for this S-NSSAI. If the AMF cannot select an    SMF (e.g. the UE provided DNN is not supported by the network, or    the UE provided DNN is not in the Subscribed DNN List for the    S-NSSAI and wildcard DNN is not included in the Subscribed DNN    list), the AMF shall reject the NAS Message containing PDU Session    Establishment Request from the UE with an appropriate cause

The AMF selects an SMF as described in 3GPP TS 23.501 clause 6.3.2 andTS 23.502 clause 4.3.2.2.3. In particular, the AMF selects an H-SMF inHPLMN using the S-NSSAI with the value defined by the HPLMN, asdescribed in 3GPP TS 23.502 clause 4.3.2.2.3. The AMF may also receivealternative H-SMFs from the NRF. The AMF stores the association of theS-NSSAI, the DNN, the PDU Session ID, the SMF ID in VPLMN as well asAccess Type of the PDU Session If the Request Type indicates “Initialrequest” or the request is due to handover from EPS or from non-3GPPaccess serving by a different AMF, the AMF stores an association of theS-NSSAI(s), the DNN, the PDU Session ID, the SMF ID as well as theAccess Type of the PDU Session.

If the Request Type is “initial request” and if the Old PDU Session IDindicating the existing PDU Session is also contained in the message,the AMF selects an SMF as described in clause 4.3.5.2 and stores anassociation of the new PDU Session ID, the S-NSSAI, the selected SMF IDas well as Access Type of the PDU Session.

If the Request Type indicates “Existing PDU Session”, the AMF selectsthe SMF based on SMF-ID received from UDM. The case where the RequestType indicates “Existing PDU Session”, and either the AMF does notrecognize the PDU Session ID or the subscription context that the AMFreceived from UDM during the Registration or Subscription Profile UpdateNotification procedure does not contain an SMF ID corresponding to thePDU Session ID constitutes an error case. The AMF updates the AccessType stored for the PDU Session.

If the Request Type indicates “Existing PDU Session” referring to anexisting PDU Session moved between 3GPP access and non-3GPP access, thenif the S-NSSAI of the PDU Session is present in the Allowed NSSAI of thetarget access type, the PDU Session Establishment procedure can beperformed in the following cases:

-   -   the SMF ID corresponding to the PDU Session ID and the AMF        belong to the same PLMN;    -   the SMF ID corresponding to the PDU Session ID belongs to the        HPLMN;    -   Otherwise the AMF shall reject the PDU Session Establishment        Request with an appropriate reject cause.

-   NOTE 2: The SMF ID includes the PLMN ID that the SMF belongs to.

The AMF shall reject a request coming from an Emergency Registered UEand the Request Type indicates neither “Emergency Request” nor “ExistingEmergency PDU Session”. When the Request Type indicates “EmergencyRequest”, the AMF is not expecting any S-NSSAI and DNN value provided bythe UE and uses locally configured values instead. The AMF stores theAccess Type of the PDU Session.

If the Request Type indicates “Emergency Request” or “Existing EmergencyPDU Session”, the AMF selects the SMF as described in 3GPP TS 23.501,clause 5.16.4.

In local breakout roaming case, if V-SMF responds to AMF indicating thatV-SMF is not able to process some part of the N1 SM information, the AMFproceeds with home routed case from this operation and may select an SMFin the VPLMN different from the V-SMF selected earlier.

-   3a. As in operation 3 of 3GPP TS 23.502 clause 4.3.2.2.1 with the    addition that:    -   The AMF also provides the identity of the H-SMF it has selected        in operation 2 and both the S-NSSAI from the Allowed NSSAI and        the corresponding Subscribed S-NSSAI. The H-SMF is provided when        the PDU Session is home-routed. The AMF may also provide the        identity of alternative H-SMFs, if it has received in operation        2.    -   The V-SMF does not use DNN Selection Mode received from the AMF        but relays this information to the H-SMF.

The AMF may include the H-PCF ID in this operation and V-SMF will passit to the H-SMF in operation 6. This will enable the H-SMF to select thesame H-PCF in operation 9a.

-   3b. This operation is the same as operation 5 of 3GPP TS 23.502    clause 4.3.2.2.1.-   4. The V-SMF selects a UPF in VPLMN as described in 3GPP TS 23.501,    clause 6.3.3.-   5. The V-SMF initiates an N4 Session Establishment procedure with    the selected V-UPF:    -   a. The V-SMF sends an N4 Session Establishment Request to the        V-UPF. If CN Tunnel Info is allocated by the SMF, the CN Tunnel        Info is provided to V-UPF in this operation.    -   b. The V-UPF acknowledges by sending an N4 Session Establishment        Response. If CN Tunnel Info is allocated by the V-UPF, the CN        Tunnel Info is provided to V-SMF in this operation.-   6. V-SMF to H-SMF: Nsmf_PDUSession_Create Request (SUPI, GPSI (if    available), DNN, S-NSSAI with the value defined by the HPLMN, PDU    Session ID, V-SMF ID, V-CN-Tunnel-Info, PDU Session Type, PCO,    Number Of Packet Filters, User location information, Access Type,    PCF ID, SM PDU DN Request Container, DNN Selection Mode, [Always-on    PDU Session Requested]). Protocol Configuration Options may contain    information that H-SMF may needs to properly establish the PDU    Session (e.g. SSC mode or SM PDU DN Request Container to be used to    authenticate the UE by the DN-AAA as defined in clause 4.3.2.3). The    H-SMF may use DNN Selection Mode when deciding whether to accept or    reject the UE request. If the V-SMF does not receive any response    from the H-SMF due to communication failure on the N16 interface,    depending on operator policy the V-SMF may create the PDU Session to    one of the alternative H-SMF(s) if additional H-SMF information is    provided in operation 3a, as specified in detail in TS 29.502 [36].-   7-12. These operations are the same as operations 4-10 in 3GPP TS    23.502 clause 4.3.2.2.1 with the following differences:    -   These operations are executed in Home PLMN;    -   The H-SMF stores an association of the PDU Session and V-SMF ID        for this PDU Session for this UE;    -   The H-SMF does not provides the Inactivity Timer to the H-UPF as        described in operation 9a in 3GPP TS 23.502 clause 4.3.2.2.1;    -   The H-SMF registers for the PDU Session ID with the UDM using        Nudm_UECM_Registration (SUPI, DNN, S-NSSAI with the value        defined by the HPLMN, PDU Session ID); and    -   Operation 5 of 3GPP TS 23.502 clause 4.3.2.2.1 is not executed.

When PCF is deployed, the SMF shall further report the PS Data Offstatus to PCF if the PS Data Off event trigger is provisioned, theadditional behaviour of SMF and PCF for 3GPP PS Data Off is defined in3GPP TS 23.503.

Operation 8 (PDU Session Authentication/Authorization) is described inmore detail below with reference to FIG. 8.

-   13. H-SMF to V-SMF: Nsmf_PDUSession_Create Response (QoS Rule(s),    QoS Flow level QoS parameters if needed for the QoS Flow(s)    associated with the QoS rule(s), PCO including session level    information that the V-SMF is not expected to understand, selected    PDU Session Type and SSC mode, H-CN Tunnel Info, QFI(s), QoS    profile(s), Session-AMBR, Reflective QoS Timer (if available),    information needed by V-SMF in case of EPS interworking such as the    PDN Connection Type, User Plane Policy Enforcement). If the PDU    Session being established was requested to be an always-on PDU    Session, the H-SMF shall indicate to the V-SMF whether the request    is accepted or not via the Always-on PDU Session Granted indication    in the response message to V-SMF. If the PDU Session being    established was not requested to be an always-on PDU Session but the    H-SMF determines that the PDU Session needs to be established as an    always-on PDU Session, the H-SMF shall indicate it to the V-SMF by    including Always-on PDU Session Granted indication that the PDU    Session is an always-on PDU Session.

The information that the H-SMF may provide is the same as defined foroperation 11 shown in 3GPP TS 23.502 FIG. 4.3.2.2.1-1.

The H-CN Tunnel Info contains the tunnel information for uplink traffictowards H-UPF.

Multiple QoS Rules and QoS Flow level QoS parameters for the QoS Flow(s)associated with the QoS rule(s) may be included in theNsmf_PDUSession_Create Response.

-   14-18. These operations are the same as operations 11-15 in 3GPP TS    23.502 clause 4.3.2.2.1 with the following differences:    -   These operations are executed in Visited PLMN;    -   The V-SMF stores an association of the PDU Session and H-SMF ID        for this PDU Session for this UE;    -   If the H-SMF indicates the PDU Session can be established as an        always-on PDU Session, the V-SMF shall further check whether the        PDU Session can be established as an always-on PDU Session based        on local policies. The V-SMF notifies the UE whether the PDU        Session is an always-on PDU Session or not via the Always-on PDU        Session Granted indication in the PDU Session Establishment        Accept message.-   19a. The V-SMF initiates an N4 Session Modification procedure with    the V-UPF. The V-SMF provides Packet detection, enforcement and    reporting rules to be installed on the V-UPF for this PDU Session,    including AN Tunnel Info, H-CN Tunnel Info and V-CN Tunnel Info.-   19b. The V-UPF provides a N4 Session Modification Response to the    V-SMF. After this operation, the V-UPF delivers any down-link    packets to the UE that may have been buffered for this PDU Session.-   20. This operation is the same as operation 17 in 3GPP TS 23.502    clause 4.3.2.2.1 except that SMF is V-SMF.-   21. This operation is same as operation 18 in 3GPP TS 23.502 clause    4.3.2.2.1.-   22. H-SMF to UE, via H-UPF and V-UPF in VPLMN: In case of PDU    Session Type IPv6 or IPv4v6, the H-SMF generates an IPv6 Router    Advertisement and sends it to the UE via N4 and the H-UPF and V-UPF.-   23. If the V-SMF received in operationl8 an indication that the    (R)AN has rejected some QFI(s) the V-SMF notifies the H-SMF via a    Nsmf_PDUSession_Update Request. The H-SMF is responsible of updating    accordingly the QoS rules and QoS Flow level QoS parameters if    needed for the QoS Flow(s) associated with the QoS rule(s) in the    UE.-   24. Unsubscribe/Deregistration: This operation is the same as    operation 20 in 3GPP TS 23.502 clause 4.3.2.2.1 except that this    operation is executed in the HPLMN.-   NOTE: The H-SMF can initiate operation 21 already after operation    13.

FIG. 8 shows an exemplary signalling flow of a PDU session establishmentauthentication/authorization procedure by a DN AAA server. Thisprocedure can correspond to operation 8 shown in FIG. 7 above, forexample. for a UE-requested PDU session based on home-routed roaming.Although the operations shown in FIG. 8 are labelled with numbers, thislabelling is only to facilitate clarity of description, and should notbe interpreted as limiting the operations to occur in the order of theirnumerical labelling. In other words, unless expressly noted otherwise,the operations shown in FIG. 8 can occur in different orders than shown,and can be combined and/or divided to form other operations. Theoperations shown in FIG. 8 are described as follows. To the extent thatthis description refers to 3GPP standards, the relevant portions ofthese standards are incorporated herein by reference.

-   0. The SMF determines that it needs to contact the DN-AAA server.    This can occur, for example, if the SMF is an H-SMF that is    contacted by a V-SMF regarding establishment of a PDU session for a    user roaming into the VPLMN, such as illustrated in FIG. 7. The SMF    identifies the DN-AAA server based on local configuration, possibly    using the SM PDU DN Request Container provided by the UE in its NAS    request.-   1. If there is no existing N4 session that can be used to carry    DN-related messages between the SMF and the DN, the SMF selects a    UPF and triggers N4 session establishment.-   2. The SMF provides a SM PDU DN Request Container received from the    UE to the DN-AAA via the UPF.-   3. When available, the SMF provides the GPSI in the signalling    exchanged with the DN-AAA.

The UPF transparently relays the message received from the SMF to theDN-AAA server.

-   NOTE 2: The content of SM PDU DN Request Container is defined in    3GPPTS 33.501.-   3a. The DN-AAA server sends an Authentication/Authorization message    towards the SMF. The message is carried via the UPF.-   3b. Transfer of DN Request Container information received from    DN-AAA towards the UE.

In non-roaming and LBO cases, the SMF invokes theNamf_Communication_N1N2MessageTransfer service operation on the AMF totransfer the DN Request Container information within N1 SM informationsent towards the UE.

In the case of Home Routed roaming, the H-SMF initiates aNsmf_PDUSession_Update service operation to request the V-SMF totransfer DN Request Container to the UE and the V-SMF invokes theNamf_Communication_N1N2MessageTransfer service operation on the AMF totransfer the DN Request Container information within N1 SM informationsent towards the UE.

-   3c. The AMF sends the N1 NAS message to the UE.-   3d-e. Transfer of DN Request Container information received from UE    towards the DN-AAA. When the UE responds with a N1 NAS message    containing DN Request Container information, the AMF informs the SMF    by invoking the Nsmf_PDUSession_UpdateSMContext service operation.    The SMF issues an Nsmf_PDUSession_UpdateSMContext response.

In the case of Home Routed roaming, the V-SMF relays the N1 SMinformation to the H-SMF via a Nsmf_PDUSession_Update service operation.

-   3f. The SMF (In HR case it is the H-SMF) sends the content of the DN    Request Container information (authentication message) to the DN-AAA    server via the UPF.

The operations 3a-f may be repeated until the DN-AAA server confirms thesuccessful authentication/authorization of the PDU Session.

-   4. The DN-AAA server confirms the successful    authentication/authorization of the PDU Session. The DN-AAA server    may provide:    -   an SM PDU DN Response Container to the SMF to indicate        successful authentication/authorization;    -   authorization information as defined in 3GPP TS 23.501 clause        5.6.6;    -   a request to get notified with the IP address(es) allocated to        the PDU Session and/or with N6 traffic routing information or        MAC address(es) used by the UE for the PDU Session; and    -   an IP address (or IPV6 Prefix) for the PDU Session.

The N6 traffic routing information is defined in 3GPP TS 23.501 clause5.6.7.

After the successful DN authentication/authorization, a session is keptbetween the SMF and the DN-AAA.

-   5. The PDU Session establishment continues and completes.-   6. If requested so in operation 4 or if configured so by local    policies, the SMF notifies the DN-AAA with the IP/MAC address(es)    and/or with N6 traffic routing information allocated to the PDU    Session together with the GPSI.

Subsequently, the SMF can notify the DN-AAA if the DN-AAA had requestedto get notifications about actions and/or conditions such as:

-   -   Allocation or release of an IPV6 Prefix for the PDU Session of        IP type or    -   Addition or removal of source MAC addresses for the PDU Session        of Ethernet type (e.g. using IPV6 multi-homing as defined in        3GPP TS 23.501 clause 5.6.4.3;    -   Change of N6 traffic routing information; and/or    -   Release of the PDU session (as described in 3GPP TS 23.502        clause 4.3.4.

The DN-AAA server may revoke the authorization for a PDU Session orupdate DN authorization data for a PDU Session. According to the requestfrom DN-AAA server, the SMF may release or update the PDU Session.

At any time after the PDU Session establishment, the DN-AAA server orSMF may initiate Secondary Re-authentication procedure for the PDUSession as specified in 3GPP TS 33.501 clause 11.1.3. Operations 3a-fare performed to transfer the Secondary Re-authentication messagebetween the UE and the DN-AAA server. The Secondary Re-authenticationprocedure may start from operation 3a (DN-AAA initiated SecondaryRe-authentication procedure) or operation 3b (SMF initiated SecondaryRe-authentication procedure). For the DN-AAA server initiated SecondaryRe-authentication, the message in operation 3a shall include GPSI, ifavailable, and the IP/MAC address(es) of the PDU session, for SMF toidentify the corresponding UE and PDU session.

Nevertheless, there are certain problems in the signalling for thehome-routed roaming scenario illustrated in FIGS. 7-8. For example, inoperation 3e shown in FIG. 8, the V-SMF is not able to sendNsmf_PDUSession_Update request to the H-SMF because the V-SMF does nothave an identifier (e.g., URI) of the resource created in H-SMF for thePDU session (referred to as “hsmfPDUSessionUri”). This problem isillustrated in the simplified signalling flow shown in FIG. 9. Forexample, in conventional operation, the V-SMF does not receive thehsmfPDUSessionUri from the H-SMF until the PDU_Session_Create Response,as illustrated in FIG. 9. Even so, merely sending the hsmfPDUSessionUrito the V-SMF in an earlier message (e.g., in PDU_Session_Update Request)is not feasible, because the V-SMF may not support such earlier deliveryand/or may be unprepared to accept the information.

Exemplary embodiments of the present disclosure address these and otherproblems, challenges, and/or issues by providing techniques for updatingthe V-SMF with the hsmfPDUSessionUri information in a manner that isboth timely and under control of the V-SMF, so that the V-SMF isexpecting to receive the hsmfPDUSessionUri when it is delivered. Thesetechniques provide various other advantages, including facilitatingcorrect operation of the secondary authentication/authorization by aDN-AAA server during PDU session establishment for home-routed roamingscenarios.

It is noted that the present application defines that the second requestcomprises one or more indicators of whether the V-SMF supportsrespective one or more indicators of whether the V-SMF supportsrespective one or more features related to receiving, from the H-SMF, anidentifier of a resource in the H-SMF that is associated with the PDUsession. It is noted that the present disclosure may also be enabledeven if the above information is not comprised by the second request. Itis noted that the V-SMF may also receive the third request comprisingthe identifier of the resource in the H-SMF, wherein the third requestbeing received before receiving any other messages from the H-SMF,irrespective of whether the one or more indicators are present in thesecond request.

The present disclosure is directed to a method, performed by a sessionmanagement function, V-SMF, of a visited public land mobile network,VPLMN, for establishing a user-requested PDU session to be routedthrough a user's home PLMN, HPLMN, the method comprising:

-   -   receiving, for example from an access management function, AMF,        in the VPLMN, a first request to establish a home-routed PDU        session, wherein the first request identifies an SMF, H-SMF, in        the HPLMN; and    -   sending, to the H-SMF, a second request to create the        home-routed PDU session, wherein the second request includes an        identifier of a resource in the V-SMF that is associated with        the PDU session.

The above enables the H-SMF to address the services of the V-SMF relatedto the PDU session e.g. PDUSession_Update Request from H-SMF to V-SMF.

In an example, the method comprises the step of receiving, from theH-SMF, a third request that includes an identifier of a resource in theH-SMF that is associated with the PDU session and allows the V-SMF toaddress services of the H-SMF related to the PDU session.

It was the insight of the inventor that the V-SMF is not able to send aPDU session update request to the H-SMF, in the home routed roaming,because the V-SMF does not have the resource URI of the resource in theH-SMF.

The present method enables the V-SMF to contact the H-SMF in thesesituations as it has received, in the third request, an identifier ofthe resource in the H-SMF that is associated with the PDU session.

In a further example, the method comprises the step of sending by theV-SMF, to the H-SMF, a fourth request for transferring an authenticationresponse from the UE using the identifier of the resource in the H-SMFthat is associated with the PDU session.

In another example, the third request being received before receivingany other messages from the H-SMF.

In a further example, any of:

-   -   the first request comprises a PDUSession_CreateSMContext        Request;    -   the second request comprises a PDUSession_Create Request; and    -   the third request comprises a PDUSession_Update Request.

Following the above, the present disclosure enables the H-SMF to addressthe services of the V-SMF related to the PDU session, e.g.PDUSession_Update Request from H-SMF to V-SMF.

In context of the present disclosure, the resource in the H-SMF that isassociated with the PDU session is, for example, directly related to theSession Management, SM, Context for service operations related with thisPDU Session.

In another example, the method further comprises the step of sending, tothe H-SMF, a PDUSession_update message for transferring anauthentication response from the UE using the identifier of the resourcein the H-SMF that is associated with the PDU session.

Examples of the disclosure are presented here below.

In an example, the third request being received before receiving anyother messages from the H-SMF.

In a further example, the first request comprises aPDUSession_CreateSMContext Request, the second request comprises aPDUSession_Create Request; and the third request comprises aPDUSession_Update Request.

In another example, the method further comprises the step of sending, tothe H-SMF, a PDUSession_update message for transferring anautherntication response from the UE using the identifier of theresource in the H-SMF that is associated with the PDU session.

In a second aspect, the present disclosure is directed to a method,performed by a session management function, H-SMF, of a home public landmobile network, HPLMN, for establishing a user-requested Protocol DataUnit, PDU, session to be routed from a user's visited PLMN, VPLMN,through the HPLMN, the method comprising:

-   -   receiving, from an SMF of the VPLMN, V-SMF, a second request to        create a home-routed PDU session, wherein the second request        includes an identifier of a resource in the V-SMF associated        with the PDU session, and    -   sending, to the V-SMF, a third request that includes the        identifier of a resource in the H-SMF that is associated with        the PDU session.

In an example, the third request is sent to said V-SMF before sendingany other messages to the V-SMF.

In a further example, the second request comprises a PDUSession_CreateRequest; and the third request comprises a PDUSession_Update Request.

In an example, the method further comprises the step of receiving, fromthe V-SMF, a PDUSession_update message for transferring anautherntication response from the UE.

In a further aspect of the present disclosure, there is provided asession management, SMF, node arranged to operate in a public landmobile network, PLMN, the session management node comprising:

-   -   a network interface configured to communicate with at least one        other SMF in at least one other PLMN;    -   processing circuitry operably coupled to the network interface        and configured to perform operations corresponding to any of the        methods; and    -   power supply circuitry configured to supply power to the SMF        node.

In an example, the session management, SMF, node is arranged to operatein a public land mobile network, PLMN, the SMF node being arranged toperform operations corresponding to any of the methods in accordancewith the present disclosure.

In a further aspect, there is provided a non-transitory,computer-readable medium storing computer-executable instructions that,when executed by processing circuitry comprising a session management,SMF, node in a public land mobile network, PLMN, configure the SMF nodeto perform operations corresponding to any of the methods in accordancewith the present disclosure.

In another aspect, there is provided a computer program productcomprising computer-executable instructions that, when executed byprocessing circuitry comprising a session management, SMF, node in apublic land mobile network, PLMN, configure the SMF node to performoperations corresponding to any of the methods in accordance with thepresent disclosure.

In some embodiments, an identifier of a resource to be created in theH-SMF for a PDU session (e.g., hsmfPDUSessionUri) can be included in thePDUSession_Update Request message sent from the H-SMF after receivingthe PDUSession_Create Request message from the V-SMF containing anidentifier of a resource in the V-SMF for the PDU session (e.g.,vsmfPDUSessionUri). This PDUSession_Update Request message correspondsto operation 3b shown in FIG. 8. In addition, however, thePDUSession_Create Request message of these embodiments includes anindicator of whether the V-SMF supports such early delivery ofhsmfPDUSessionUri in the PDUSession_Update Request message.

Upon receiving the the PDUSession_Create Request message, the H-SMF candetermine from the indicator whether the V-SMF supports early deliver ofhsmfPDUSessionUri. If it determines that the V-SMF supports earlydelivery, the H-SMF includes the hsmfPDUSessionUri in thePDUSession_Update Request message. If the indicator is absent orindicates that the V-SMF does not support early delivery, the H-SMF doesnot include the hsmfPDUSessionUri in the PDUSession_Update Requestmessage. For example, the H-SMF can instead include hsmfPDUSessionUri inthe PDUSession_Create Response message, where the V-SMF conventionallyexpects to receive it.

FIG. 10 shows an exemplary signalling flow diagram according to theseexemplary embodiments. In FIG. 10, the indicator is called“supportedFeatures.” For example, the indicator can be a particularsub-field of a “supportedFeatures” field that relates to variousfeatures supported by the V-SMF on the interface with the H-SMF.

In other embodiments, before the H-SMF sends a PDUSession_CreateResponse message including hsmfPDUSessionUri, the H-SMF can send aPDUSession_Update message to the V-SMF to update the resource alreadybeing created in V-SMF for the same PDU session (e.g., by addressingvsmfPduSessionUri). In such embodiments, however, the V-SMF should senda PDUSession_Update Response message only after it receives a responsefrom UE that include an authentication response, which is transferredvia the PDUSession_Update SmContext Request message sent from the AMF.This is because the V-SMF has to use PDU Session update response messageto transfer the PDU Session authentication complete message from UE,since the V-SMF is not able to initiate a PDUSession_Update (to transferthe authentication response) towards the H-SMF before it receivesPDUSession_Create response which contains hsmfPDUSessionUri.

In these embodiments, two other indicators can be used in the messagesto indiate support for such features. First, the PDUSession_UpdateRequest message sent by the V-SMF can include a first indicator that theV-SMF should delay sending the PDUSession_Update Response message untilafter receiving the authentication response from the UE via the AMF.Second, the PDUSession_Create Response message sent by the V-SMF caninclude a second indicator of whether the V-SMF supports: 1) processinga PDU Session Update request from the H-SMF for a PDU session for whichthe resource has not been fully established in the H-SMF (i.e., H-SMFhas not sent PDU Session Create Response with hsmfPDUSessionUri,together with 2) a delayed response under control of the H-SMF via thefirst indicator. For convenience, these two features will be referred tocollectively as “delayed sending” or “delayed response.”

Upon receiving the the PDUSession_Create Request message, the H-SMF candetermine from the second indicator whether the V-SMF supports delayedsending of the PDUSession_Update Response message. If it determines thatthe V-SMF supports delayed sending, the H-SMF can include the firstindicator in the PDUSession_Update Request message. If the secondindicator is absent or indicates that the V-SMF does not support delayedsending, the H-SMF does not include the first indicator in thePDUSession_Update Request message.

Upon receiving the PDUSession_Update Request message, the V-SMF candetermine whether the first indicator is present and, if so, whether itindicates that the V-SMF should delay sending the PDUSession_UpdateResponse message. If it determines that the H-SMF requests delayedsending, the V-SMF can delay sending the message accordingly. If thefirst indicator is absent or indicates that the H-SMF does not requestdelayed sending, the V-SMF can send the message without waiting for theUE response, in the manner expected by the H-SMF.

FIG. 11 shows an exemplary signalling flow diagram according to theseexemplary embodiments. In FIG. 11, the first indicator is called“delayedResponse” and the second indicator is called“supportedFeatures,” similar to FIG. 10. For example, the firstindicator can be a particular sub-field of a “supportedFeatures” fieldthat relates to various features supported by the V-SMF on the interfacewith the H-SMF.

In other exemplary embodiments, the H-SMF can respond to the presence orabsence of the “supportedFeatures” indicator in the PDUSession CreateRequest message in the manner discussed above with respect to thevarious embodiments. In some embodiments, the H-SMF can also performadditional actions if the indicator is absent or indicates that neitherof the two alternatives (e.g., early deliver or delayed response) aresupported by the V-SMF. For example, the H-SMF can defer and/or delaycommunication towards AAA for the authentication procedure. In otherwords, the H-SMF can proceed with PDU session creation as if theauthentication was successful, and then trigger AAA procedure after thePDU session is created, i.e., after sending PDU Session Create responsewith acceptance. This is illustrated in FIG. 11 by the optional delay ofthe AAA Request/Response messages.

FIG. 12 illustrates an exemplary method and/or procedure forestablishing a user-requested PDU session to be routed through theuser's HPLMN, according to various exemplary embodiments of the presentdisclosure. The exemplary method and/or procedure shown in FIG. 12 canbe performed by a session management function (e.g., SMF) or node in avisited PLMN that is different that the HPLMN of the user establishingthe PDU session. Although the exemplary method and/or procedure isillustrated in FIG. 12 by blocks in a particular order, this order isexemplary and the operations corresponding to the blocks can beperformed in different orders, and can be combined and/or divided intoblocks and/or operations having different functionality than shown inFIG. 12. Furthermore, the exemplary method and/or procedure shown inFIG. 12 can be complementary to other exemplary methods and/orprocedures disclosed herein, such that they are capable of being usedcooperatively to provide the benefits, advantages, and/or solutions toproblems described hereinabove. Optional blocks and/or operations areindicated by dashed lines.

The exemplary method and/or procedure can include the operations ofblock 1210, where the V-SMF can receive, from an access managementfunction (AMF) in the HPLMN, a first request to establish a home-routedPDU session, wherein the first request identifies an SMF (H-SMF) in theHPLMN. The exemplary method and/or procedure can also include theoperations of block 1220, where the V-SMF can send, to the H-SMF, asecond request to create the home-routed PDU session. The second requestcan include an identifier of a resource in the V-SMF associated with thePDU session. The second request can also include one or more indicatorsof whether the V-SMF supports respective one or more features related toreceiving, from the H-SMF, an identifier of a resource in the H-SMF thatis associated with the PDU session.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports early delivery of the identifier of the resourcein the H-SMF. In such embodiments, the exemplary method and/or procedurecan also include the operations of block 1230, where the V-SMF canreceive from the H-SMF, a third request that includes the identifier ofthe resource in the H-SMF, the third request being received beforereceiving any other messages from the H-SMF.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports delayed sending of a response to a thirdrequest. In such embodiments, the exemplary method and/or procedure canalso include the operations of block 1240, where the V-SMF can receive,from the H-SMF, a third request comprising a further indicator that theV-SMF should delay sending a response to the third request until afterreceiving, from the AMF, authentication information relating to theuser. In such embodiments, the exemplary method and/or procedure canalso include the operations of block 1250, where the V-SMF can, afterreceiving the authentication information from the AMF, send the responseto the third request to the H-SMF. In such embodiments, the exemplarymethod and/or procedure can also include the operations of block 1260,where the V-SMF can subsequently receive a response, to the secondrequest, comprising the identifier of the resource in the H-SMF.

In some embodiments, the first request comprises aPDUSession_CreateSMContext Request, the second request comprises aPDUSession_Create Request, and the third request comprises aPDUSession_Update Request.

FIG. 13 illustrates an exemplary method and/or procedure forestablishing a user-requested PDU session to be routed from a user'sVPLMN through the user's HPLMN, according to various exemplaryembodiments of the present disclosure. The exemplary method and/orprocedure shown in FIG. 13 can be performed by a session managementfunction (e.g., SMF) or node in a HPLMN (e.g., a H-SMF) that isdifferent from the VPLMN where the user is initiating the PDU session.Although the exemplary method and/or procedure is illustrated in FIG. 13by blocks in a particular order, this order is exemplary and theoperations corresponding to the blocks can be performed in differentorders, and can be combined and/or divided into blocks having differentfunctionality than shown in FIG. 13. Furthermore, the exemplary methodand/or procedure shown in FIG. 13 can be complementary to otherexemplary methods and/or procedures disclosed herein, such that they arecapable of being used cooperatively to provide the benefits, advantages,and/or solutions to problems described hereinabove. Optional blocksand/or operations are indicated by dashed lines.

The exemplary method and/or procedure can include the operations ofblock 1310, where the H-SMF can receive, from the V-SMF, a secondrequest to create a home-routed PDU session. The second request caninclude an identifier of a resource in the V-SMF that is associated withthe PDU session. The second request can also include one or moreindicators of whether the V-SMF supports respective one or more featuresrelated to receiving, from the H-SMF, an identifier of a resource in theH-SMF that is associated with the PDU session. The exemplary methodand/or procedure can also include the operations of block 1320, wherethe H-SMF can, based on the one or more indicators, send one or moremessages to the V-SMF, with each message including one of the following:a further indicator; and the identifier of the resource in the H-SMF.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports early delivery of the identifier of the resourcein the H-SMF. In such embodiments, the operations of block 1320 caninclude the operations of sub-block 1322, where the H-SMF can send, tothe V-SMF, a third request that includes the identifier of the resourcein the H-SMF, the third request being sent before sending any othermessages to the V-SMF. In other words, the third request can be one ofthe one or more messages.

In some embodiments, the one or more indicators can include an indicatorthat the V-SMF supports delayed sending of a response to a thirdrequest. In such embodiments, the operations of block 1320 can includethe operations of sub-block 1324, where the H-SMF can send, to theV-SMF, a third request comprising a further indicator that the V-SMFshould delay sending a response to the third request until afterreceiving authentication information relating to the user. In otherwords, the third request can be one of the one or more messages.

In such embodiments, the operations of block 1320 can include theoperations of sub-block 1326, where the H-SMF can receive the responseto the third request from the V-SMF. In such embodiments, the one ormore messages sent to the V-SMF include a response, to the secondrequest, comprising the identifier of the resource in the H-SMF, withthe response to the second request being sent after receiving theresponse to the third request.

In some embodiments, the exemplary method and/or procedure can alsoinclude the operations of block 1330, where the H-SMF can delay anauthentication procedure related to the PDU session until after sendingthe one or more messages. In such embodiments, the delaying can be basedon the one or more indicators being absent from the second request, orthe one or more indicators having values that indicate that the V-SMFdoes not support the respective one or more features.

In some embodiments, the first request comprises aPDUSession_CreateSMContext Request, the second request comprises aPDUSession_Create Request, and the third request comprises aPDUSession_Update Request.

Although the subject matter described herein can be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 14.For simplicity, the wireless network of FIG. 14 only depicts network1406, network nodes 1460 and 1460 b, and WDs 1410, 1410 b, and 1410 c.In practice, a wireless network can further include any additionalelements suitable to support communication between wireless devices orbetween a wireless device and another communication device, such as alandline telephone, a service provider, or any other network node or enddevice. Of the illustrated components, network node 1460 and wirelessdevice (WD) 1410 are depicted with additional detail. The wirelessnetwork can provide communication and other types of services to one ormore wireless devices to facilitate the wireless devices' access toand/or use of the services provided by, or via, the wireless network.

The wireless network can comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork can be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network can implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or Zig Bee standards.

Network 1406 can comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 1460 and WD 1410 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network can comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that canfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations can be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and can then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station can be a relay node or a relay donor nodecontrolling a relay. A network node can also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station can also be referred to as nodes in adistributed antenna system (DAS).

Further examples of network nodes include multi-standard radio (MSR)equipment such as MSR BSs, network controllers such as radio networkcontrollers (RNCs) or base station controllers (BSCs), base transceiverstations (BTSs), transmission points, transmission nodes,multi-cell/multicast coordination entities (MCEs), core network nodes(e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes(e.g., E-SMLCs), and/or MDTs. As another example, a network node can bea virtual network node as described in more detail below. Moregenerally, however, network nodes can represent any suitable device (orgroup of devices) capable, configured, arranged, and/or operable toenable and/or provide a wireless device with access to the wirelessnetwork or to provide some service to a wireless device that hasaccessed the wireless network.

In FIG. 14, network node 1460 includes processing circuitry 1470, devicereadable medium 1480, interface 1490, auxiliary equipment 1484, powersource 1486, power circuitry 1487, and antenna 1462. Although networknode 1460 illustrated in the example wireless network of FIG. 14 canrepresent a device that includes the illustrated combination of hardwarecomponents, other embodiments can comprise network nodes with differentcombinations of components. It is to be understood that a network nodecomprises any suitable combination of hardware and/or software needed toperform the tasks, features, functions and methods and/or proceduresdisclosed herein. Moreover, while the components of network node 1460are depicted as single boxes located within a larger box, or nestedwithin multiple boxes, in practice, a network node can comprise multipledifferent physical components that make up a single illustratedcomponent (e.g., device readable medium 1480 can comprise multipleseparate hard drives as well as multiple RAM modules).

Similarly, network node 1460 can be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which can each have their ownrespective components. In certain scenarios in which network node 1460comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components can be shared among severalnetwork nodes. For example, a single RNC can control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, can in someinstances be considered a single separate network node. In someembodiments, network node 1460 can be configured to support multipleradio access technologies (RATs). In such embodiments, some componentscan be duplicated (e.g., separate device readable medium 1480 for thedifferent RATs) and some components can be reused (e.g., the sameantenna 1462 can be shared by the RATs). Network node 1460 can alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 1460, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies can be integrated into thesame or different chip or set of chips and other components withinnetwork node 1460.

Processing circuitry 1470 can be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 1470 can include processinginformation obtained by processing circuitry 1470 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry 1470 can comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 1460 components, such as device readable medium 1480, network node1460 functionality. For example, processing circuitry 1470 can executeinstructions stored in device readable medium 1480 or in memory withinprocessing circuitry 1470. Such functionality can include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 1470 can include asystem on a chip (SOC).

In some embodiments, processing circuitry 1470 can include one or moreof radio frequency (RF) transceiver circuitry 1472 and basebandprocessing circuitry 1474. In some embodiments, radio frequency (RF)transceiver circuitry 1472 and baseband processing circuitry 1474 can beon separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry 1472 and baseband processing circuitry 1474 can beon the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device can be performed by processing circuitry 1470executing instructions stored on device readable medium 1480 or memorywithin processing circuitry 1470. In alternative embodiments, some orall of the functionality can be provided by processing circuitry 1470without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry 1470 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry 1470 alone or toother components of network node 1460, but are enjoyed by network node1460 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1480 can comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that can be used byprocessing circuitry 1470. Device readable medium 1480 can store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 1470 and, utilized by network node 1460. Devicereadable medium 1480 can be used to store any calculations made byprocessing circuitry 1470 and/or any data received via interface 1490.In some embodiments, processing circuitry 1470 and device readablemedium 1480 can be considered to be integrated.

Interface 1490 is used in the wired or wireless communication ofsignalling and/or data between network node 1460, network 1406, and/orWDs 1410. As illustrated, interface 1490 comprises port(s)/terminal(s)1494 to send and receive data, for example to and from network 1406 overa wired connection. Interface 1490 also includes radio front endcircuitry 1492 that can be coupled to, or in certain embodiments a partof, antenna 1462. Radio front end circuitry 1492 comprises filters 1498and amplifiers 1496. Radio front end circuitry 1492 can be connected toantenna 1462 and processing circuitry 1470. Radio front end circuitrycan be configured to condition signals communicated between antenna 1462and processing circuitry 1470. Radio front end circuitry 1492 canreceive digital data that is to be sent out to other network nodes orWDs via a wireless connection. Radio front end circuitry 1492 canconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 1498and/or amplifiers 1496. The radio signal can then be transmitted viaantenna 1462. Similarly, when receiving data, antenna 1462 can collectradio signals which are then converted into digital data by radio frontend circuitry 1492. The digital data can be passed to processingcircuitry 1470. In other embodiments, the interface can comprisedifferent components and/or different combinations of components.

In certain alternative embodiments, network node 1460 may not includeseparate radio front end circuitry 1492, instead, processing circuitry1470 can comprise radio front end circuitry and can be connected toantenna 1462 without separate radio front end circuitry 1492. Similarly,in some embodiments, all or some of RF transceiver circuitry 1472 can beconsidered a part of interface 1490. In still other embodiments,interface 1490 can include one or more ports or terminals 1494, radiofront end circuitry 1492, and RF transceiver circuitry 1472, as part ofa radio unit (not shown), and interface 1490 can communicate withbaseband processing circuitry 1474, which is part of a digital unit (notshown).

Antenna 1462 can include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 1462 can becoupled to radio front end circuitry 1490 and can be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 1462 can comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna can be used to transmit/receive radio signalsin any direction, a sector antenna can be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna canbe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna can be referred to as MIMO. In certain embodiments, antenna 1462can be separate from network node 1460 and can be connectable to networknode 1460 through an interface or port.

Antenna 1462, interface 1490, and/or processing circuitry 1470 can beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals can be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 1462, interface 1490, and/or processing circuitry 1470 can beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalscan be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 1487 can comprise, or be coupled to, power managementcircuitry and can be configured to supply the components of network node1460 with power for performing the functionality described herein. Powercircuitry 1487 can receive power from power source 1486. Power source1486 and/or power circuitry 1487 can be configured to provide power tothe various components of network node 1460 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 1486 can either be included in,or external to, power circuitry 1487 and/or network node 1460. Forexample, network node 1460 can be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 1487. As a further example, power source 1486can comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 1487. Thebattery can provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, can also beused.

Alternative embodiments of network node 1460 can include additionalcomponents beyond those shown in FIG. 14 that can be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 1460 can include user interface equipment to allow and/orfacilitate input of information into network node 1460 and to allowand/or facilitate output of information from network node 1460. This canallow and/or facilitate a user to perform diagnostic, maintenance,repair, and other administrative functions for network node 1460.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD can be used interchangeably herein with user equipment (UE).Communicating wirelessly can involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD can be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD can be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc.

A WD can support device-to-device (D2D) communication, for example byimplementing a 3GPP standard for sidelink communication,vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I),vehicle-to-everything (V2X) and can in this case be referred to as a D2Dcommunication device. As yet another specific example, in an Internet ofThings (IoT) scenario, a WD can represent a machine or other device thatperforms monitoring and/or measurements, and transmits the results ofsuch monitoring and/or measurements to another WD and/or a network node.The WD can in this case be a machine-to-machine (M2M) device, which canin a 3GPP context be referred to as an MTC device. As one particularexample, the WD can be a UE implementing the 3GPP narrow band internetof things (NB-IoT) standard. Particular examples of such machines ordevices are sensors, metering devices such as power meters, industrialmachinery, or home or personal appliances (e.g.,refrigerators,televisions, etc.) personal wearables (e.g., watches, fitness trackers,etc.). In other scenarios, a WD can represent a vehicle or otherequipment that is capable of monitoring and/or reporting on itsoperational status or other functions associated with its operation. AWD as described above can represent the endpoint of a wirelessconnection, in which case the device can be referred to as a wirelessterminal. Furthermore, a WD as described above can be mobile, in whichcase it can also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 1410 includes antenna 1411, interface1414, processing circuitry 1420, device readable medium 1430, userinterface equipment 1432, auxiliary equipment 1434, power source 1436and power circuitry 1437. WD 1410 can include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies can be integrated into the same or different chipsor set of chips as other components within WD 1410.

Antenna 1411 can include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 1414. In certain alternative embodiments, antenna 1411 can beseparate from WD 1410 and be connectable to WD 1410 through an interfaceor port. Antenna 1411, interface 1414, and/or processing circuitry 1420can be configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals can be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 1411 can beconsidered an interface.

As illustrated, interface 1414 comprises radio front end circuitry 1412and antenna 1411. Radio front end circuitry 1412 comprise one or morefilters 1418 and amplifiers 1416. Radio front end circuitry 1414 isconnected to antenna 1411 and processing circuitry 1420, and can beconfigured to condition signals communicated between antenna 1411 andprocessing circuitry 1420. Radio front end circuitry 1412 can be coupledto or a part of antenna 1411. In some embodiments, WD 1410 may notinclude separate radio front end circuitry 1412; rather, processingcircuitry 1420 can comprise radio front end circuitry and can beconnected to antenna 1411. Similarly, in some embodiments, some or allof RF transceiver circuitry 1422 can be considered a part of interface1414. Radio front end circuitry 1412 can receive digital data that is tobe sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry 1412 can convert the digital data into a radiosignal having the appropriate channel and bandwidth parameters using acombination of filters 1418 and/or amplifiers 1416. The radio signal canthen be transmitted via antenna 1411. Similarly, when receiving data,antenna 1411 can collect radio signals which are then converted intodigital data by radio front end circuitry 1412. The digital data can bepassed to processing circuitry 1420. In other embodiments, the interfacecan comprise different components and/or different combinations ofcomponents.

Processing circuitry 1420 can comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 1410components, such as device readable medium 1430, WD 1410 functionality.Such functionality can include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry1420 can execute instructions stored in device readable medium 1430 orin memory within processing circuitry 1420 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 1420 includes one or more of RFtransceiver circuitry 1422, baseband processing circuitry 1424, andapplication processing circuitry 1426. In other embodiments, theprocessing circuitry can comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry1420 of WD 1410 can comprise a SOC. In some embodiments, RF transceivercircuitry 1422, baseband processing circuitry 1424, and applicationprocessing circuitry 1426 can be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry1424 and application processing circuitry 1426 can be combined into onechip or set of chips, and RF transceiver circuitry 1422 can be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 1422 and baseband processing circuitry1424 can be on the same chip or set of chips, and application processingcircuitry 1426 can be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 1422,baseband processing circuitry 1424, and application processing circuitry1426 can be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 1422 can be a part of interface1414. RF transceiver circuitry 1422 can condition RF signals forprocessing circuitry 1420.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD can be provided by processingcircuitry 1420 executing instructions stored on device readable medium1430, which in certain embodiments can be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality canbe provided by processing circuitry 1420 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 1420 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 1420 alone or to other components ofWD 1410, but are enjoyed by WD 1410 as a whole, and/or by end users andthe wireless network generally.

Processing circuitry 1420 can be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 1420, can include processinginformation obtained by processing circuitry 1420 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 1410, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 1430 can be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 1420. Device readable medium 1430 can includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that can be used by processing circuitry 1420. In someembodiments, processing circuitry 1420 and device readable medium 1430can be considered to be integrated.

User interface equipment 1432 can include components that allow and/orfacilitate a human user to interact with WD 1410. Such interaction canbe of many forms, such as visual, audial, tactile, etc. User interfaceequipment 1432 can be operable to produce output to the user and toallow and/or facilitate the user to provide input to WD 1410. The typeof interaction can vary depending on the type of user interfaceequipment 1432 installed in WD 1410. For example, if WD 1410 is a smartphone, the interaction can be via a touch screen; if WD 1410 is a smartmeter, the interaction can be through a screen that provides usage(e.g., the number of gallons used) or a speaker that provides an audiblealert (e.g., if smoke is detected). User interface equipment 1432 caninclude input interfaces, devices and circuits, and output interfaces,devices and circuits. User interface equipment 1432 can be configured toallow and/or facilitate input of information into WD 1410, and isconnected to processing circuitry 1420 to allow and/or facilitateprocessing circuitry 1420 to process the input information. Userinterface equipment 1432 can include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a USB port, or other input circuitry. User interface equipment1432 is also configured to allow and/or facilitate output of informationfrom WD 1410, and to allow and/or facilitate processing circuitry 1420to output information from WD 1410. User interface equipment 1432 caninclude, for example, a speaker, a display, vibrating circuitry, a USBport, a headphone interface, or other output circuitry. Using one ormore input and output interfaces, devices, and circuits, of userinterface equipment 1432, WD 1410 can communicate with end users and/orthe wireless network, and allow and/or facilitate them to benefit fromthe functionality described herein.

Auxiliary equipment 1434 is operable to provide more specificfunctionality which may not be generally performed by WDs. This cancomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 1434 can vary depending on the embodiment and/or scenario.

Power source 1436 can, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, can also be used. WD 1410 can further comprise power circuitry1437 for delivering power from power source 1436 to the various parts ofWD 1410 which need power from power source 1436 to carry out anyfunctionality described or indicated herein. Power circuitry 1437 can incertain embodiments comprise power management circuitry. Power circuitry1437 can additionally or alternatively be operable to receive power froman external power source; in which case WD 1410 can be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 1437 can also in certain embodiments be operable to deliverpower from an external power source to power source 1436. This can be,for example, for the charging of power source 1436. Power circuitry 1437can perform any converting or other modification to the power from powersource 1436 to make it suitable for supply to the respective componentsof WD 1410.

FIG. 15 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE can represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE canrepresent a device that is not intended for sale to, or operation by, anend user but which can be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 15200 can be any UE identified bythe 3^(rd) Generation Partnership Project (3GPP), including a NB-IoT UE,a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 1500, as illustrated in FIG. 15, is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3^(rd) Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE can be used interchangeable. Accordingly, although FIG.15 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 15, UE 1500 includes processing circuitry 1501 that isoperatively coupled to input/output interface 1505, radio frequency (RF)interface 1509, network connection interface 1511, memory 1515 includingrandom access memory (RAM) 1517, read-only memory (ROM) 1519, andstorage medium 1521 or the like, communication subsystem 1531, powersource 1533, and/or any other component, or any combination thereof.Storage medium 1521 includes operating system 1523, application program1525, and data 1527. In other embodiments, storage medium 1521 caninclude other similar types of information. Certain UEs can utilize allof the components shown in FIG. 15, or only a subset of the components.The level of integration between the components can vary from one UE toanother UE. Further, certain UEs can contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 15, processing circuitry 1501 can be configured to processcomputer instructions and data. Processing circuitry 1501 can beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 1501 can include twocentral processing units (CPUs). Data can be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 1505 can beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 1500 can be configured touse an output device via input/output interface 1505. An output devicecan use the same type of interface port as an input device. For example,a USB port can be used to provide input to and output from UE 1500. Theoutput device can be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 1500 can be configured to use aninput device via input/output interface 1505 to allow and/or facilitatea user to capture information into UE 1500. The input device can includea touch-sensitive or presence-sensitive display, a camera (e.g., adigital camera, a digital video camera, a web camera, etc.), amicrophone, a sensor, a mouse, a trackball, a directional pad, atrackpad, a scroll wheel, a smartcard, and the like. Thepresence-sensitive display can include a capacitive or resistive touchsensor to sense input from a user. A sensor can be, for instance, anaccelerometer, a gyroscope, a tilt sensor, a force sensor, amagnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device can bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 15, RF interface 1509 can be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 1511 can beconfigured to provide a communication interface to network 1543 a.Network 1543 a can encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 1543 a can comprise aWi-Fi network. Network connection interface 1511 can be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 1511 can implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions can share circuit components, software or firmware,or alternatively can be implemented separately.

RAM 1517 can be configured to interface via bus 1502 to processingcircuitry 1501 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 1519 canbe configured to provide computer instructions or data to processingcircuitry 1501. For example, ROM 1519 can be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium1521 can be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 1521 can be configured toinclude operating system 1523, application program 1525 such as a webbrowser application, a widget or gadget engine or another application,and data file 1527. Storage medium 1521 can store, for use by UE 1500,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 1521 can be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 1521 can allow and/or facilitate UE 1500 to accesscomputer-executable instructions, application programs or the like,stored on transitory or non-transitory memory media, to off-load data,or to upload data. An article of manufacture, such as one utilizing acommunication system can be tangibly embodied in storage medium 1521,which can comprise a device readable medium.

In FIG. 15, processing circuitry 1501 can be configured to communicatewith network 1543 b using communication subsystem 1531. Network 1543 aand network 1543 b can be the same network or networks or differentnetwork or networks. Communication subsystem 1531 can be configured toinclude one or more transceivers used to communicate with network 1543b. For example, communication subsystem 1531 can be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.15,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver caninclude transmitter 1533 and/or receiver 1535 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 1533and receiver 1535 of each transceiver can share circuit components,software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 1531 can include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 1531 can include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 1543 b can encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network1543 b can be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 1513 can be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 1500.

The features, benefits and/or functions described herein can beimplemented in one of the components of UE 1500 or partitioned acrossmultiple components of UE 1500. Further, the features, benefits, and/orfunctions described herein can be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem1531 can be configured to include any of the components describedherein. Further, processing circuitry 1501 can be configured tocommunicate with any of such components over bus 1502. In anotherexample, any of such components can be represented by programinstructions stored in memory that when executed by processing circuitry1501 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components can be partitionedbetween processing circuitry 1501 and communication subsystem 1531. Inanother example, the non-computationally intensive functions of any ofsuch components can be implemented in software or firmware and thecomputationally intensive functions can be implemented in hardware.

FIG. 16 is a schematic block diagram illustrating a virtualizationenvironment 1600 in which functions implemented by some embodiments canbe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which can includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein canbe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 1600 hosted byone or more of hardware nodes 1630. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node can beentirely virtualized.

The functions can be implemented by one or more applications 1620 (whichcan alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 1620 are runin virtualization environment 1600 which provides hardware 1630comprising processing circuitry 1660 and memory 1690. Memory 1690contains instructions 1695 executable by processing circuitry 1660whereby application 1620 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 1600, comprises general-purpose orspecial-purpose network hardware devices 1630 comprising a set of one ormore processors or processing circuitry 1660, which can be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device can comprise memory 1690-1 which can benon-persistent memory for temporarily storing instructions 1695 orsoftware executed by processing circuitry 1660. Each hardware device cancomprise one or more network interface controllers (NICs) 1670, alsoknown as network interface cards, which include physical networkinterface 1680. Each hardware device can also include non-transitory,persistent, machine-readable storage media 1690-2 having stored thereinsoftware 1695 and/or instructions executable by processing circuitry1660. Software 1695 can include any type of software including softwarefor instantiating one or more virtualization layers 1650 (also referredto as hypervisors), software to execute virtual machines 1640 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 1640, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and can be run by acorresponding virtualization layer 1650 or hypervisor. Differentembodiments of the instance of virtual appliance 1620 can be implementedon one or more of virtual machines 1640, and the implementations can bemade in different ways.

During operation, processing circuitry 1660 executes software 1695 toinstantiate the hypervisor or virtualization layer 1650, which cansometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 1650 can present a virtual operating platform thatappears like networking hardware to virtual machine 1640.

As shown in FIG. 16, hardware 1630 can be a standalone network node withgeneric or specific components. Hardware 1630 can comprise antenna 16225and can implement some functions via virtualization. Alternatively,hardware 1630 can be part of a larger cluster of hardware (e.g.,such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 16100, which, among others, oversees lifecyclemanagement of applications 1620.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV can be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 1640 can be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 1640, and that part of hardware 1630 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 1640, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 1640 on top of hardware networking infrastructure1630 and corresponds to application 1620 in FIG. 16.

In some embodiments, one or more radio units 16200 that each include oneor more transmitters 16220 and one or more receivers 16210 can becoupled to one or more antennas 16225. Radio units 16200 can communicatedirectly with hardware nodes 1630 via one or more appropriate networkinterfaces and can be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system 16230 which can alternatively be used for communicationbetween the hardware nodes 1630 and radio units 16200.

With reference to FIG. 17, in accordance with an embodiment, acommunication system includes telecommunication network 1710, such as a3GPP-type cellular network, which comprises access network 1711, such asa radio access network, and core network 1714. Access network 1711comprises a plurality of base stations 1712 a, 1712 b, 1712 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 1713 a, 1713 b, 1713 c. Each base station1712 a, 1712 b, 1712 c is connectable to core network 1714 over a wiredor wireless connection 1715. A first UE 1791 located in coverage area1713 c can be configured to wirelessly connect to, or be paged by, thecorresponding base station 1712 c. A second UE 1792 in coverage area1713 a is wirelessly connectable to the corresponding base station 1712a. While a plurality of UEs 1791, 1792 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to the

Telecommunication network 1710 is itself connected to host computer1730, which can be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 1730 can beunder the ownership or control of a service provider, or can be operatedby the service provider or on behalf of the service provider.Connections 1721 and 1722 between telecommunication network 1710 andhost computer 1730 can extend directly from core network 1714 to hostcomputer 1730 or can go via an optional intermediate network 1720.Intermediate network 1720 can be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 1720,if any, can be a backbone network or the Internet; in particular,intermediate network 1720 can comprise two or more sub-networks (notshown).

The communication system of FIG. 17 as a whole enables connectivitybetween the connected UEs 1791, 1792 and host computer 1730. Theconnectivity can be described as an over-the-top (OTT) connection 1750.Host computer 1730 and the connected UEs 1791, 1792 are configured tocommunicate data and/or signaling via OTT connection 1750, using accessnetwork 1711, core network 1714, any intermediate network 1720 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 1750 can be transparent in the sense that the participatingcommunication devices through which OTT connection 1750 passes areunaware of routing of uplink and downlink communications. For example,base station 1712 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 1730 to be forwarded (e.g., handed over) to a connected UE1791. Similarly, base station 1712 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 1791towards the host computer 1730.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 18. In communication system1800, host computer 1810 comprises hardware 1815 including communicationinterface 1816 configured to set up and maintain a wired or wirelessconnection with an interface of a different communication device ofcommunication system 1800. Host computer 1810 further comprisesprocessing circuitry 1818, which can have storage and/or processingcapabilities. In particular, processing circuitry 1818 can comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. Host computer 1810 furthercomprises software 1811, which is stored in or accessible by hostcomputer 1810 and executable by processing circuitry 1818. Software 1811includes host application 1812. Host application 1812 can be operable toprovide a service to a remote user, such as UE 1830 connecting via OTTconnection 1850 terminating at UE 1830 and host computer 1810. Inproviding the service to the remote user, host application 1812 canprovide user data which is transmitted using OTT connection 1850.

Communication system 1800 can also include base station 1820 provided ina telecommunication system and comprising hardware 1825 enabling it tocommunicate with host computer 1810 and with UE 1830. Hardware 1825 caninclude communication interface 1826 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 1800, as well as radiointerface 1827 for setting up and maintaining at least wirelessconnection 1870 with UE 1830 located in a coverage area (not shown inFIG. 18) served by base station 1820. Communication interface 1826 canbe configured to facilitate connection 1860 to host computer 1810.Connection 1860 can be direct or it can pass through a core network (notshown in FIG. 18) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 1825 of base station 1820 can also includeprocessing circuitry 1828, which can comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 1820 further has software 1821 storedinternally or accessible via an external connection.

Communication system 1800 can also include UE 1830 already referred to.Its hardware 1835 can include radio interface 1837 configured to set upand maintain wireless connection 1870 with a base station serving acoverage area in which UE 1830 is currently located. Hardware 1835 of UE1830 can also include processing circuitry 1838, which can comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 1830 further comprisessoftware 1831, which is stored in or accessible by UE 1830 andexecutable by processing circuitry 1838. Software 1831 includes clientapplication 1832. Client application 1832 can be operable to provide aservice to a human or non-human user via UE 1830, with the support ofhost computer 1810. In host computer 1810, an executing host application1812 can communicate with the executing client application 1832 via OTTconnection 1850 terminating at UE 1830 and host computer 1810. Inproviding the service to the user, client application 1832 can receiverequest data from host application 1812 and provide user data inresponse to the request data. OTT connection 1850 can transfer both therequest data and the user data. Client application 1832 can interactwith the user to generate the user data that it provides.

It is noted that host computer 1810, base station 1820 and UE 1830illustrated in FIG. 18 can be similar or identical to host computer1730, one of base stations 1712 a, 1712 b, 1712 c and one of UEs 1791,1792 of FIG. 17, respectively. This is to say, the inner workings ofthese entities can be as shown in FIG. 18 and independently, thesurrounding network topology can be that of FIG. 17.

In FIG. 18, OTT connection 1850 has been drawn abstractly to illustratethe communication between host computer 1810 and UE 1830 via basestation 1820, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure can determine the routing, which it can be configured tohide from UE 1830 or from the service provider operating host computer1810, or both. While OTT connection 1850 is active, the networkinfrastructure can further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 1870 between UE 1830 and base station 1820 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 1830 using OTT connection1850, in which wireless connection 1870 forms the last segment. Moreprecisely, the exemplary embodiments disclosed herein can improveflexibility for the network to monitor end-to-end quality-of-service(QoS) of data flows, including their corresponding radio bearers,associated with data sessions between a user equipment (UE) and anotherentity, such as an OTT data application or service external to the 5Gnetwork. These and other advantages can facilitate more timely design,implementation, and deployment of 5G/NR solutions. Furthermore, suchembodiments can facilitate flexible and timely control of data sessionQoS, which can lead to improvements in capacity, throughput, latency,etc. that are envisioned by 5G/NR and important for the growth of OTTservices.

A measurement procedure can be provided for the purpose of monitoringdata rate, latency and other network operational aspects on which theone or more embodiments improve. There can further be an optionalnetwork functionality for reconfiguring OTT connection 1850 between hostcomputer 1810 and UE 1830, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 1850 can be implemented in software 1811and hardware 1815 of host computer 1810 or in software 1831 and hardware1835 of UE 1830, or both. In embodiments, sensors (not shown) can bedeployed in or in association with communication devices through whichOTT connection 1850 passes; the sensors can participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 1811, 1831 can compute or estimate the monitoredquantities. The reconfiguring of OTT connection 1850 can include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 1820, and it can be unknownor imperceptible to base station 1820. Such procedures andfunctionalities can be known and practiced in the art. In certainembodiments, measurements can involve proprietary UE signalingfacilitating host computer 1810's measurements of throughput,propagation times, latency and the like. The measurements can beimplemented in that software 1811 and 1831 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 1850 while it monitors propagation times, errors etc.

FIG. 19 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which, in some exemplary embodiments, can be thosedescribed with reference to FIGS. 17 and 18. For simplicity of thepresent disclosure, only drawing references to FIG. 19 will be includedin this section. In step 1910, the host computer provides user data. Insubstep 1911 (which can be optional) of step 1910, the host computerprovides the user data by executing a host application. In step 1920,the host computer initiates a transmission carrying the user data to theUE. In step 1930 (which can be optional), the base station transmits tothe UE the user data which was carried in the transmission that the hostcomputer initiated, in accordance with the teachings of the embodimentsdescribed throughout this disclosure. In step 1940 (which can also beoptional), the UE executes a client application associated with the hostapplication executed by the host computer.

FIG. 20 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which can be those described with reference to FIGS. 17and 18. For simplicity of the present disclosure, only drawingreferences to FIG. 20 will be included in this section. In step 2010 ofthe method, the host computer provides user data. In an optional substep(not shown) the host computer provides the user data by executing a hostapplication. In step 2020, the host computer initiates a transmissioncarrying the user data to the UE. The transmission can pass via the basestation, in accordance with the teachings of the embodiments describedthroughout this disclosure. In step 2030 (which can be optional), the UEreceives the user data carried in the transmission.

FIG. 21 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which can be those described with reference to FIGS. 17and 18. For simplicity of the present disclosure, only drawingreferences to FIG. 21 will be included in this section. In step 2110(which can be optional), the UE receives input data provided by the hostcomputer. Additionally or alternatively, in step 2120, the UE providesuser data. In substep 2121 (which can be optional) of step 2120, the UEprovides the user data by executing a client application. In substep2111 (which can be optional) of step 2110, the UE executes a clientapplication which provides the user data in reaction to the receivedinput data provided by the host computer. In providing the user data,the executed client application can further consider user input receivedfrom the user. Regardless of the specific manner in which the user datawas provided, the UE initiates, in substep 2130 (which can be optional),transmission of the user data to the host computer. In step 2140 of themethod, the host computer receives the user data transmitted from theUE, in accordance with the teachings of the embodiments describedthroughout this disclosure.

FIG. 22 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which can be those described with reference to FIGS. 17and 18. For simplicity of the present disclosure, only drawingreferences to FIG. 22 will be included in this section. In step 2210(which can be optional), in accordance with the teachings of theembodiments described throughout this disclosure, the base stationreceives user data from the UE. In step 2220 (which can be optional),the base station initiates transmission of the received user data to thehost computer. In step 2230 (which can be optional), the host computerreceives the user data carried in the transmission initiated by the basestation.

The term unit, as used herein, can have conventional meaning in thefield of electronics, electrical devices and/or electronic devices andcan include, for example, electrical and/or electronic circuitry,devices, modules, processors, memories, logic solid state and/ordiscrete devices, computer programs or instructions for carrying outrespective tasks, procedures, computations, outputs, and/or displayingfunctions, and so on, as such as those that are described herein.

The invention claimed is:
 1. A method, performed by a session managementfunction (V-SMF) of a visited public land mobile network (VPLMN) forestablishing a user-requested PDU session to be routed through theuser's home PLMN (HPLMN) the method comprising: receiving, a firstrequest to establish a home-routed PDU session, wherein the firstrequest identifies an SMF, H-SMF, in the HPLMN; sending, to the H-SMF, asecond request to create the home-routed PDU session, wherein the secondrequest includes an identifier of a resource in the V-SMF that isassociated with the PDU session; and receiving, from the H-SMF inresponse to the second request, an identifier of a resource in the H-SMFthat is associated with the PDU session and allows the V-SMF to addressservices of the H-SMF related to the PDU session.
 2. The method of claim1, further comprising: sending, to the H-SMF, a fourth request fortransferring an authentication response from the user equipment (UE) ofthe user, using the identifier of the resource in the H-SMF that isassociated with the PDU session.
 3. The method of claim 1, wherein theidentifier of the resource in the H-SMF is received before receiving anyother messages from the H-SMF.
 4. The method of claim 1, wherein: thefirst request comprises a PDUSession_CreateSMContext Request; the secondrequest comprises a PDUSession_Create Request; and the identifier of theresource in the H-SMF is received in a PDUSession_Update Request.
 5. Themethod of claim 2, wherein the fourth request comprises aPDUSession_update message.
 6. A method, performed by a sessionmanagement function (H-SMF) of a home public land mobile network (HPLMN)of a user, for establishing a user-requested Protocol Data Unit, PDU,session to be routed from the user's visited PLMN (VPLMN) through theHPLMN, the method comprising: receiving, from an SMF of the VPLMN,V-SMF, a second request to create a home-routed PDU session, wherein thesecond request includes an identifier of a resource in the V-SMFassociated with the PDU session; and sending, to the V-SMF in responseto the second request, an identifier of a resource in the H-SMF that isassociated with the PDU session.
 7. The method of claim 6, wherein theidentifier of the resource in the H-SMF is sent to the V-SMF beforesending any other messages to the V-SMF.
 8. The method of claim 6,wherein: the second request comprises a PDUSession_Create Request; andthe identifier of the resource in the H-SMF is received in aPDUSession_Update Request.
 9. The method of claim 6, further comprisingreceiving, from the V-SMF, a PDUSession_update message for transferringan authentication response from a user equipment (UE) of the user.
 10. Asession management (SMF) node arranged to operate in a public landmobile network (PLMN), the session management node comprising: a networkinterface configured to communicate with at least one other SMF node inat least one other PLMN; processing circuitry operably coupled to thenetwork interface and configured to perform operations corresponding tothe methods of claim 1; and power supply circuitry configured to supplypower to the SMF node.
 11. A non-transitory, computer-readable mediumstoring computer-executable instructions that, when executed byprocessing circuitry comprising a session management (SMF) node in apublic land mobile network (PLMN), configure the SMF node to performoperations corresponding to the method of claim
 1. 12. A method,performed by a session management function (V-SMF) of a visited publicland mobile network (VPLMN) for establishing a user-requested PDUsession to be routed through the user's home PLMN (HPLMN), the methodcomprising: receiving, from an Access Management Function, AMF, in theVPLMN a PDUSession_CreateSMContext Request to establish a home-routedPDU session, wherein the first request identifies an SMF, H-SMF, in theHPLMN; sending, to the H-SMF, a PDUSession_Create Request to create thehome-routed PDU session, wherein the request includes an identifier of aresource in the V-SMF that is associated with the PDU session and allowsthe H-SMF to address services of the V-SMF related to the PDU session;receiving, from the H-SMF, a PDUSession_Update Request that includes anidentifier of a resource in the H-SMF that is associated with the PDUsession and allows the V-SMF to address services of the H-SMF related tothe PDU session; and sending, to the H-SMF, a PDUSession_Update Requestfor transferring an authentication response from the user equioment, UE,of the user, using the identifier of the resource in the H-SMF that isassociated with the PDU session.
 13. A method, performed by a sessionmanagement function, H-SMF, of a user's home public land mobile network,HPLMN, for establishing a user-requested PDU session to be routedthrough a visited PLMN, VPLMN, to the HPLMN the method comprising:receiving, from a V-SMF, a PDUSession_Create Request to create thehome-routed PDU session, wherein the request includes an identifier of aresource in the V-SMF that is associated with the PDU session and allowsthe H-SMF to address services of the V-SMF related to the PDU session;sending, to the V-SMF, a PDUSession_Update Request that includes anidentifier of a resource in the H-SMF that is associated with the PDUsession and allows the V-SMF to address services of the H-SMF related tothe PDU session; and receiving, from V-SMF, a PDUSession_Update Requestfor transferring an authentication response from the user equipment (UE)of the user, using the identifier of the resource in the H-SMF that isassociated with the PDU session.
 14. A method performed by a visitedpublic land mobile network (VPLMN) for establishing a user-requested PDUsession to be routed through a user's home PLMN (HPLMN) for a userequipment (UE) of the user, operational connected to the VPLMN, themethod comprising: receiving a first request to create the home-routedPDU session; sending, to the HPLMN, a second request to create thehome-routed PDU session, wherein the second request includes anidentifier of a resource in the VPLMN that is associated with the PDUsession and allows the HPLMN to address services of the VPLMN related tothe PDU session; receiving from the HPLMN in response to the secondrequest, an identifier of a resource in the HPLMN that is associatedwith the PDU session and allows the VPLMN to address services of theHPLMN related to the PDU session; and receiving, from the VPLMN, afourth request for transferring an authentication response from the UEusing the identifier of the resource in the HPLMN that is associatedwith the PDU session.
 15. A method performed by a user's home publicland mobile network, HPLMN, for establishing a user-requested PDUsession to be routed through visited PLMN, VPLMN, to the HPLMN for auser equipment (UE) of the user, operational connected to the VPLMN, themethod comprising: receiving from the VPLMN, a second request to createthe home-routed PDU session, wherein the second request includes anidentifier of a resource in the VPLMN that is associated with the PDUsession and allows the HPLMN to address services of the VPLMN related tothe PDU session; sending to the VPLMN in response to the second request,an identifier of a resource in the HPLMN that is associated with the PDUsession and allows the VPLMN to address services of the HPLMN related tothe PDU session; and receiving, from the VPLMN, a fourth request fortransferring an authentication response from the UE using the identifierof the resource in the HPLMN that is associated with the PDU session.